Resuming packet services in a mobile network

ABSTRACT

This disclosure relates generally to resuming packet services in a mobile network. A device, method, and/or system may include switching, with user equipment, from communicating with a first radio access network to communicating with a second radio access network, setting, with a processor of the user equipment, a register of the user equipment to initiate packet services with the first radio access network, and transmitting, with the user equipment, a request to a core network node of the first radio access network to resume communications with the first radio access network based, at least in part, on the register.

This application is a continuation of U.S. patent application Ser. No.14/141,67, filed Dec. 26, 2013, which claims the benefit of priorityunder 35 U.S.C. 119(e) to U.S. Provisional Patent Application Ser. No.61/841,230, filed on Jun. 28, 2013, each of which is incorporated hereinby reference in its entirety.

TECHNICAL FIELD

The disclosure herein relates generally to devices, systems, and/ormethods for resuming packet services in a mobile network.

BACKGROUND

In a conventional public land mobile network (PLMN), such as accordingto the 3^(rd) Generation Partnership Project (3GPP), various radioaccess networks (RANs), such as a General Packet Radio Subsystem EvolvedRadio Access Network (GERAN), a Universal Mobile TelecommunicationsSystem Terrestrial Radio Access Network (UTRAN), and an Evolved-UTRAN(E-UTRAN) may be connected to a common core network and may providevarious and different services. For instance, GERAN or UTRAN may providevoice services, solely or in part. E-UTRAN, by contrast, may providepacket services, either solely or in part.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a mobile network, in an example embodiment.

FIG. 2 is a block diagram of a mobile network architecture forcircuit-switched fallback, in an example embodiment.

FIG. 3 is a data flow showing the resumption of data packets via theMME, in an example embodiment.

FIG. 4 is a data flow showing a suspend and resume procedure forintra-SGSN communication, in an example embodiment.

FIG. 5 is a data flow for a combined 2G/3G SGSN serving both a GERANcell and a UTRAN cell, in an example embodiment.

FIG. 6 is a message flow for a dedicated 2G SGSN and a dedicated 3G SGSNserving the GERAN cells and the UTRAN cells, respectively, in an exampleembodiment.

FIG. 7 is a flowchart for storing radio access technology information,in an example embodiment.

FIG. 8 is a block diagram illustrating components of a machine,according to some example embodiments.

DESCRIPTION OF EMBODIMENTS

The following description and the drawings sufficiently illustratespecific embodiments to enable those skilled in the art to practicethem. Other embodiments may incorporate structural, logical, electrical,process, and other changes. Portions and features of some embodimentsmay be included in, or substituted for, those of other embodiments.Embodiments set forth in the claims encompass all available equivalentsof those claims.

FIG. 1 is a block diagram of a mobile network 100, in an exampleembodiment. In various examples, the mobile network 100 is an evolvedpacket core network supporting, without limitation, GERAN, UTRAN, and/orE-UTRAN. It is to be understood that, while various components may bethe particular elements as illustrated, the components may be replacedwith similar or suitable components for various related mobile networksand mobile network environments.

User equipment 102 (as noted, also referred to as a Mobile Station (MS))is communicatively coupled via a radio interface 104 (e.g., Long TermEvolution (LTE-Uu)) to an E-UTRAN 106 system. The E-UTRAN 106 may hecommunicatively coupled via a S1-MME (Mobility Management Entity) link108 to a MME 110 and via a S1-U link 112 to a Serving Gateway 114. TheMME 110 may be directly connected to the Serving Gateway 114 via an S11link 115 and may be connected via a S3 link 116 to a Serving GeneralPacket Radio Subsystem Support Node (SGSN) 118, which is itselfconnected via an S4 link 120 to the Serving Gateway 114. The MME 110 mayinclude an internal S10 link 122 and an S6a link 124 to a High SpeedSerial (HSS) interface node 126.

The Serving Gateway 114 may be connected via an S12 link 128 to one ormore UTRAN 130 and GERAN 132 networks. The Serving Gateway 114 mayfurther be connected via an S5 link 134 to a public data network (PDN)gateway 136. The PDN gateway 136 may be connected via a link 138 to apolicy and changing rules function (PCRF) node 140 and via a SGi link142 to an operator's IP services 144, such as an IP Multimedia Subsystem(IMS). The PCRF node 140 may be connected to the operator's IP services144 via a link 146.

FIG. 2 is a block diagram of a mobile network architecture 200 forcircuit-switched fallback, in an example embodiment. The architecture200 may operate with respect to the mobile network 100 or any suitablemobile network.

The UE 102 is communicatively coupled or coupleable to a UTRAN cell 202,a GERAN cell 204, and an E-UTRAN cell 206. The UTRAN cell 202 and theGERAN cell 204 are coupled or coupleable to the SGSN 118 and mobileswitching center (MSC) server 208. The E-UTRAN cell 206 is coupled orcoupleable to the MME 110. The MME 110 is coupled or coupleable to theSGSN 118 and the MSC server 208.

The GERAN 132 and UTRAN 130 RANs may be connected to a circuit-switched(CS) domain of the network 100, such as may be embodied in thearchitecture 200. For circumstances in which UE 102 is in or iscommunicating via the E-UTRAN 206 cell when the subscriber wants tosetup a CS voice call, the mobile network 100 may include a CS fallback(CSFB). In CSFB, the UE 102 in the E-UTRAN 206 cell may signal to thecore network 100 that it wants to set up a CS call or that the UE 102wants to respond to a paging for a CS call. The mobile network 100and/or the architecture 200 may the redirect the UE 102 to a GERAN 204or UTRAN 202 cell, such as via a packet-switched (PS) handover, via a“release with redirection” procedure, or via a network-assisted cellchange over (CCO). In such examples, the UE 102 can set up the mobileoriginating call or receive the mobile terminating call via the MSCserver 208. Once the CS call is released in GERAN 204 and/or UTRAN 202cells, the UE 102 may return to the E-UTRAN cell 206 either on its own(e.g., via cell re-selection) or with the help of the GERAN and/or UTRAN(e.g., if, during the release of the radio connection for the CS callthe GERAN 204 and/or UTRAN 202 cells commands the UE 102 to immediatelyselect a specific E-UTRAN cell 206).

During the CS call, if the UE 102 is in a GERAN cell 204 and the UE 102or the GERAN cell 204 is not supporting the simultaneous use of CSservices and packet services (e.g., because a dual transfer mode (DTM)feature is not present or not supported), then the network 100 and/orthe architecture 200 may suspend packets services for the UE 102. Insuch a circumstance, downlink packets may not be delivered to the UE 102but may be forwarded by a packet data network gateway (PDN-GW) towardthe UE 102, potentially unnecessarily consuming network 100 and/orarchitecture 200 resources. In an example, the UE 102 and/or one of thecore network nodes (e.g., the MME 110 and/or the SGSN 118, asappropriate) may inform a serving gateway (S-GW) and/or the PDN-GW thatthe gateways should no longer forward downlink user packets from the UE102. Additionally or alternatively, the MME 110 or SGSN 118 maydeactivate dedicated packet bearers which are used for real-timeservices. Such services may require that user data packets are deliveredwithin a relatively short time.

When the CS call is released or when, during the CS call the UE 102 ishanded over to a cell where CS services and packet services can be usedsimultaneously, the UE 102 or the network 100 and/or architecture 200may signal to the S-GW and/or the PDN-GW that the gateways may resumepacket services (e.g., the gateways may resume forwarding downlink userplane packets form the user device 102).

In various examples, for signaling to suspend the packet services whilethe UE 102 is in a GERAN cell 204 a standard for the mobile network 100,such as the 3GPP standard, may provide two procedures: suspensioninitiated by the MME 110 and suspension initiated by the UE 102 (e.g.,via the SGSN 118). The procedures may include variants dependent, e.g.,on whether the CSFB was performed to a GERAN 204 or a UTRAN 202 targetcell, whether the CSFB was performed via PS handover or via release withredirection or CCO, whether an idle mode signaling reduction (ISR) wasactivated before the CSFB, and whether the SGSN 118 serving the GERANcell 204 and/or the UTRAN cell 202 is the SGSN 118 to which the UE 102is registered.

Correspondingly, there are two different procedures to resume packetservices when the UE 102 returns to the E-UTRAN cell 206, one usingsignaling via the MME 110 and one using signaling via the SGSN 118.However, due to multiple potential scenarios by which reconnection mayhappen, there are cases in which both primary resumption procedures ofthe 3GPP standard may fail in resuming packet services. In such cases,the packet services may remain suspended and the UE 102 may remainunreachable for mobile terminated packet services. For instance, if theUE 102 is registered for an IP multimedia subsystem (IMS) other thanVoLTE, e.g., IMS messaging or short message service (SMS) over internetprotocol (IP), a mobile terminated instant message or short message maynot be delivered to the UE 102 because the signaling for such servicesmay utilize session initiation protocol (SIP) and the packet bearer usedto transfer the Sip signaling messages has been suspended.

The UE 102 includes a wireless transceiver 210, a processor 212, andelectronic memory 214 including a register. The transceiver isconfigured to communicate with the UTRAN cell 202, the GERAN cell 204,and the E-UTRAN cell 206. The processor 212 is configured to control, atleast in part, an operation of the UE 102 generally and the components210, 214 thereof. The processor 212 may be a microprocessor, acontroller, or other dedicated hardware, as known in the art. Theelectronic memory 214 may be or include registers implemented accordingto any of a variety of electronic memory or other technologies suitablefor implementing data registers known in the art.

FIG. 3 is a data flow 300 showing the resumption of data packets via theMME 110, in an example embodiment. Resumption of packet services mayoccur via the MME 110, as noted above. When the UE 102 returns to theE-UTRAN 206 and packet services were suspended during the CS call, thenthe UE 102 may perform a combined tracking area updating procedure bysending a tracking area update (TAU) request message 302 to the MME 110(see, e.g., TS 23.272, subclauses 6.5 and 7.6, and TS 24.301, subclauses5.5.3.2.2). In circumstances where the TAU request message 302 to theMME 110 initiates a resume/modify bearers message 304 towards the S-GW306, the S-GW may interpret this as an implicit resume and may informthe PDN-GW accordingly (see, e.g., TS 23.401, subclause 5.3.3.2, steps 9and 13).

In various cases, the UE 102 context in the MME 110 is not marked as“suspended” and the MME 110 also does not initiate any TAU-relatedsignaling towards the S-GW 306 or the SGSN 118. The MME 110 may, incertain examples, mark the UE 102 context as “suspended” if, and in somecircumstances only if, the CSFB is performed via release withredirection or CCO (e.g., no via PS handover) and the eNode-B 308indicates to the MME 110 that in the target cell the UE 102 is notavailable for packet services. In such circumstances, the target cellfor the CSFB may be a GERAN cell 204 and one or more of the UE 102 andthe GERAN cell 204 are not supporting dual transfer mode (DTM). As aresult, if the CSFB is performed via PS handover or if the target cellis a UTRAN cell 202 the MME 110 will not mark the UE 102 context assuspended.

In an example, if ISR has been activated and the UE 102 sends the TAUrequest message 302 to the MME 110 to which the UE 102 is alreadyregistered, then the MME 110 may not initiate any TAU-related signalingtoward he S-GW 306 and/or the SGSN 118. Overall, if the CSFB isperformed via PS handover or if the target cell is a UTRAN cell 202, andif ISR remains activated during the CS call and, after release of thecall, the UE 102 returns to the same MME 110, the resume via the MME 110may not work according to conventional mobile network 100 protocols.

In an example, the mobile network 100 includes a protocol such that invarious examples, when the UE returns to E-UTRAN and packet serviceswere suspended during the CS call, then the UE may perform a combinedTAU procedure by sending a TAU request message to the MME 110 (FIG. 3;see, also, TS 232.272, subclauses 6.5 and 7.6, and TS 24.301, subclause5.5.3.2.2). In an example, before the UE initiates the combined TAUprocedure (e.g., before the UE 102 formats the TAU request message), theUE 102 may deactivate ISR locally, e.g., if the value of the UE 102internal control parameter Temporary Identity used in Next update (TIN)is “RAT-related”, then the UE 102 may change the value to “P-TemporaryMobile Subscriber Identity” (P-TMSI).

In various examples, if the TIN is set to P-TMSI, the UE 102 populatesthe contents of the TAU request message so as to cause the MME 110 toinitiate TAU-related signaling toward the SGSN 118 and the S-GW 306,thus resuming packet services. In an example, the UE 102 does notperform the local deactivation of ISR (e.g., for resumption of packetservices) if the UE 102 can assume that the MME 110 marked in the UE 102context as suspended, such as if the target cell of the CSFB procedurewas a GERAN cell 204 and the CSFB was performed by a release withredirection or CCO.

Referring to the packet flow 300, if the UE 102 sets the TIN to P-TMSIbefore sending the TAU request message 302, then the UE 102 populates anglobally unique temporary identity (GUTI) information element in the TAUrequest message 302 with a GUIT mapped from a P-TMSI and the relatedRAI. This may cause or force the MME 110 to exchange signaling messagewith the SGSN 118 (e.g., an “old” SGSN 118, such as a 3G SGSN, asdisclosed herein; see, also, TS 23.401, subclause 5.3.3.2, steps 4, 5,and 7; context request, context response, and context acknowledge) andwith the S-GW 306 (Id, steps 9 and 13, modify bearer request and modifybearer response). When the S-GW 306 receives the modify bearer requestor modify access bearer request message, then the S-GW 306 may interpretsuch requests as an implicit request to resume packet services and mayinform the PDN-GW accordingly. During TAU signaling, the MME 110 canimmediately re-establish ISR with the UE 102, the old SGSN 118 (e.g.,the 3G SGSN), and the S-GW 306.

In various examples, ISR may not be activated for a UE 102 registeringfor CSFB. In various examples, base station controller (BSC) behaviormay be modified. In such an example, if the GPRS resume was notsuccessful, then the BSC could avoid including redirection informationto E-UTRAN in a channel release message (disclosed herein). The UE 102may remain on the GERAN cell 204 and have the opportunity to perform arouting area update procedure to resume packet services. In an example,the MME 110 behavior may be modified, such as, in an network supportingGERAN, when the UE 102 performs CSFB, the MME 110 may mark the UE 102context as suspended.

In various examples, the mobile network 100 may avoid circumstances ofother networks in which packets services may not be resumed, though theUE 102 may perform a TAU procedure. The mobile network 100 may includeelements of conventional networks operating according to conventionalstandards and certain conventional protocols. The mobile network 100 mayinclude three (3) additional messages exchanged between the MME 110 andthe SGSN 118. However, the additional messages may be limited tocircumstances where the UE 102 actually suspended packet services duringthe CSFB and where IRS is activated (e.g., if there is no GERANconnected to the core network or if the PLMN does not activate ISR,packet services may not be suspended anyway). The additional signal mayfurther be limited to cases where the MME 110 did not mark the UE 102context as suspended.

FIG. 4 is a data flow 400 showing a suspend and resume procedure forintra-SGSN 118 communication, in an example embodiment. The data flow400 may be implemented by the network 100 or by a network that does notnecessarily include the protocols described herein with respect to thenetwork 100.

A dedicated mode 402 may be established between the UE 102, a basestation subsystem (BSS) 404, the SGSN 118, and the MSC 208. The UE 102may transmit a suspend message 406 to the BSS 404. The BSS 404 maytransmit a suspend message 408 to the SGSN 118. The SGSN 118 may replywith a suspend acknowledgement message 410. Upon initiation of aresumption procedure, the BSS 404 may transmit a resume message 412 tothe SGSN 118. The SGSN 118 may reply with a resume acknowledgementmessage 414. The BSS 404 may transmit a channel release message 416 tothe UE 102, which may then transmit a routing area update request 418 tothe SGSN 118.

If the target cell for the CSFB is a GERAN cell 204 and the UE 102 andthe GERAN cell 204 do not support DTM, the UE 102 may initiate a suspendprocedure to the SGSN 118, as detailed above. If ISR is activated, theneither the SGSN 118 receiving the suspend message 408 from the BSS 404initiates a suspend procedure toward the S-GW and/or the PDN-GW 306 or,if the UE 102 is registered to a different SGSN 118 (e.g., a previouslyregistered SGSN 118), the SGSN 118 may forward the suspend request tothe previous SGSN 118 which may then initiate the suspended proceduretowards the S-GW and/or the PDN-GW 306 (see, e.g., TS 23.272 subclauses6.2, step 3c, and subclause 6.3, steps 7 and 8). In various examples,when ISR is activated the MME 110 is not informed by the SGSN 118 or theS-GW 306 that the packet bearers have been suspended. The UE 102 mayinitiate a suspend procedure, as detailed above, toward the SGSN 118also if, later during the CSFB call the UE 102 performs a handover to aGERAN cell 204 and the UE 102 or the GERAN cell 204 do not support DTM.

In various examples, after termination of the CS call the UE 102 mayresume PS services (e.g., according to TS 23.060). In various examples,if the UE 102 remains on UTRAN/GERAN after the CS voice call isterminated the UE 102 may perform normal mobility management procedures(e.g., as defined in TS 23.060 [3] and TS 24.008 [21]). In certainexamples, resuming PS services may not occur according to BSS-SGSNsignaling and the UE may not initiate normal mobility managementprocedures in GERAN/UTRAN.

For instance, if intra-SGSN was suspended due to a CS inter-systemhandover (e.g., handover of a CS call from UTRAN to GERAN, after CSFBfrom E-UTRAN to UTRAN via. PS handover), then the resume via BSS-SGSNsignaling may not occur or may not, in certain circumstances, bepossible due to the change of a radio system s e, e.g., TS 23.060,subclause 16.2.1.2.1).

FIG. 5 is a data flow 500 for a combined 2G/3G SGSN 502 serving both aGERAN cell 204 and a UTRAN cell 202, in an example embodiment. The dataflow 500 may be implemented by the network 100 or by a network that doesnot necessarily include the protocols described herein with respect tothe network 100.

An intersystem handover message 504 may be exchanged between and amongthe UE 102, the BSS 404, the 2G/3G SGSN 502, a serving radio networksubsystem 504 (SRNS, e.g., a base station subsystem equivalent forUTRAN), and the MSC 208. The UE 102 may send a suspend message 506 tothe BSS 404. The BSS 404 may transmit a suspend message 508 to the 2G/3GSGSN 502. The SGSN 502 may forward an SRNS context request 510 to theSRNS 504. The SRNS 504 may transmit an SRNS context response 512 to theSGSN 502. The SGSN 502 may transmit a suspend acknowledgement message514 to the BSS 404. The BSS 404 may transmit a resume message 516 to theSGSN 502. In the illustrated example, the SGSN 502 may reply with aresume non-acknowledgement message 518. The BSS 404 may transmit achannel release message 520 to the UE 102. The UE 102 may transmit arouting area update request 522 to the SGSN 502.

Thus, the resume message 516 and the resume non-acknowledgement message518 may cause the UE 102 to initiate a routing area update requestprocedure to resume packet services. However, in certain circumstances,when the channel release message includes a cell selection indicatorafter release of some or all TCH and SDCCH information elements whichmay command the UE 102 to select an E-UTRAN cell, then the UE 102 maynot be able to initiate the routing area updating procedure to resumepacket services, even if the channel release message 520 does notinclude an indication that a general packet radio subsystem (GPRS)resumption was successful.

FIG. 6 is a message flow 600 for a dedicated 2G SGSN 602 and a dedicated3G SGSN 604 serving the GERAN cells 204 and the UTRAN cells 202,respectively, in an example embodiment. Thus, while the message flow 500of FIG. 5 is applicable for the combined 2G/3G SGSN 502, the messageflow 600 may be applicable to separate and dedicated SGSNs 118 (see.e.g., TS 23.060, subclause 16.2.1.2.2). The data flow 600 may beimplemented by the network 100 or by a network that does not necessarilyinclude the protocols described herein with respect to the network 100.

In the illustrated example, the UE 102, the BSS 404, the 2G SGSN 602,the 3G SGSN 604, the SRNS 504, and the MSC 208 communicate according toan intersystem handover message 606. The UE 102 transmits a suspendmessage 608 to the BSS 404. The BSS 404 transmits a suspend message 610to the 2G SGSN 602. The 2G SGSN 602 transmits a suspend request message612 to the 3G SGSN 604. The 3G SGSN 604 transmits a SRNS context requestmessage 614 to the SRNS 504. The SRNS 504 transmits a SRNS contextresponse message 616 to the 3G SGNS 604. The 3G SGSN 604 transmits asuspend response message 618 to the 2G SGSN 602. The 2G SGSN 602transmits a suspend acknowledge message 620 to the BSS 404. The BSS 404then transmits a resume message 622 to the 2G SGSN 602. The 2G SGSN 602transmits a suspend non-acknowledge message 624 to the BSS 404. The BSS404 transmits a channel release message 626 to the UE 102. The UE 102transmits a routing area update request 628 to the 2G SGSN 602.

In the above example, the 3G SGSN 604 may be an established or firstSGSN 118, e.g., the UE 102 is registered to the 3G SGSN 604 and to theMME 110 (e.g., as ISR is activated), and the CSFB target cell is a UTRANcell 202 served by the 3G SGSN 604. During the CS call the UE 102 mayperform CS inter-system handover from UTRAN to GERAN and the suspendmessage 608, 610 may be received by the 2G SGSN 602. In variousexamples, if the resume via SGSN 118 involves an inter-RAT change or ifmore than one SGSN 118 is involved, and if the network 100 performs arelease with immediate redirection to E-UTRAN, then the resume via anSGSN 118 may not work.

In an example scenario referring to FIG. 2 and according to one or moreof the message flows 300, 400, 500, 600, the UE 102 is in the E-UTRAINcell 206. The UE 102 registered to the MME 110 and to the SGSN 118 andISR is activated. The UE 102 sends an extended service request messageto the MME 110 to initiate a CSFB call or to respond to paging for anCSFB call. The network 100 and/or the architecture 200 performs CSFB toa UTRAN target cell 202. The UE 102 may he available for PS services inthe UTRAN target cell 202. In such a circumstance, the MME 110 may notmark the UE 102 context as suspended.

The UTRAN target cell 202 may be served by the SGSN 118 and below to aregistered routing area identity (RAI). In such an example, the UE 102may not initiate a routing area updating procedure. The ISR may remainactivated. In various examples, if the RAI changes due to the CSFB theUE 102 may perform a normal routing area update even if a network modeof operation (NMO) is NMO I; in such an example, ISR may remainactivated if the SGSN 118 does not change.

During a CS call, the UE may perform a CS handover to the GERAN cell 204not supporting DTM. The UE 102 may initiate a suspend procedure. If theGERAN cell 204 is served by a 2G/3G SGSN 502 the 2G/3G SGSN 502 mayinitiate suspension of the packet bearers toward the S-GW/PDN-GW 306. Ifthe GERAN cell 204 is served by a different SGSN 118 (e.g., a 2G SGSN602), the SGSN 118 may forward the suspend request to the 2G/3G SGSN502, which may initiate the suspension of the packet bearers toward theS-GW/PDN-GW 306. In such circumstances, the MME 1120 may not be informedabout the suspension.

When the CS call is released, the MSC server 208 informs a BSC of theBSS 404 that the call was initiated as a CSFB call, e.g., by providing aCSFB indication. The BSC may utilize this information and includes inthe channel release message an indication to select an E-UTRAN cell 206.The indication may be to immediately select the E-UTRAN cell 206. Beforesending the channel release message to the UE 102, the BSC may send theresume message to the SGSN 118, but due to the inter-RAT change (e.g.,after PS handover to the UTRAN target cell 202), the resume may not hepossible and the SGSN 118 may respond with a resume non-acknowledgemessage. Thus, the BSC may initiate in the channel release message alsothat GPRS resumption was not successful. In various examples, if theGERAN cell 204 is served by a 2G SGSN 602 different from the 3G SGSN604, the 2G SGSN 602 may not forward the suspend request to the 3G SGSN604 but may respond with the resume non-acknowledge message.

The UE 102 may receive the channel release message. A radio resource(RR) control of the UE 102 may react to the cell selection informationand trigger selection of the E-UTRAN cell 206. Additionally, the RR mayinform a GPRS mobility manager (GMM) in the UE 102 that GPRS resumptionwas not successful. Because the UE 102 may not be in the UTRAN/GERANcells 202, 204, GMM may not initiate a routing area updating procedureto resume packet services. Instead, the UE 102 may initiate a trackingarea updating procedure. ISR may still be activated in the UE 102.

The TAU request message may be received by the same MME 110 to which theUE 102 was registered. As ISR may still be activated and the UE 102context may not have been marked as suspended, the MME 110 may only senda TAU accept message to the UE 102 but may not initiate any orsubstantially any signaling toward the 3G SGSN 604 or the S-GW 306. Thepacket services may thus remain suspended. A periodic tracking areaupdate or other tracking area update during which IRS remains activateddoes not result in a resumption of the packet services. In suchcircumstances, the UE 102 may remain unreachable for a longer time.Conversely, a routing area update or a service request via E-UTRAN,e.g., if the UE 102 wants to transmit uplink user data, may result in aresumption of packets services.

The failures to resume packet services detailed herein may not beapplicable to the mobile network 100 that implements the protocolsdescribed herein (e.g., with respect to FIG. 3 above). In particular,the mobile network 100 may include the protocol to deactivate ISRlocally described herein. Thus, the mobile network 100 may resume packetservices in the circumstances described herein in which the network 100or other networks that do not deactivate ISR according to the protocoldescribed herein may not resume packet services.

FIG. 7 is a flowchart for storing radio access technology information,in an example embodiment. The flowchart may be used with respect to themobile network 100 or any other suitable network or system.

At 700, user equipment, such as a transceiver of the user equipment, isswitched from communicating with a first radio access network tocommunicating with a second radio access network.

At 702, a register of the user equipment is set, with the processor ofthe user equipment, to initiate packet services with the first radioaccess network. In an example, the register is a temporary identityregister configured to provide an identity of the user equipment forreconnecting with the first radio access network. In an example, settingthe register to initiate packet services is based, at least in part, onan initial setting of the register being based on a radio accesstechnology. In an example, the user equipment and the first radio accessnetwork are configured to communicate according to the radio accesstechnology. In an example, setting the register to initiate packetservices is not performed if the second radio access network is at leastone of a global system for mobile communications (GSM) radio accessnetwork and at least one of the switching was a release with redirectiona cell change order.

At 704, the processor of the user equipment configures the request basedon the register and a protocol.

At 706, a request is transmitted with the user equipment to a corenetwork node of the first radio access network to resume communicationswith the first radio access network based, at least in part, on theregister. In an example, the request is based, at least in part, on ageographic characteristic of the mobile network. In an example, thegeographic characteristic of the mobile network is a tracking area ofthe network and wherein the request is a request to perform a trackingarea update procedure with the first radio access network.

At 708, communication is resumed with the first radio access network isbased, at least in part, on packet services. In an example, resumingcommunication with the first radio access network is based, at least inpart, on packet services.

FIG. 8 is a block diagram illustrating components of a machine 800,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 8 shows a diagrammatic representation of the machine800 in the example form of a computer system and within whichinstructions 824 (e.g., software) for causing the machine 800 to performany one or more of the methodologies discussed herein may be executed.In alternative embodiments, the machine 800 operates as a standalonedevice or may be connected (e.g., networked) to other machines. In anetworked deployment, the machine 800 may operate in the capacity of aserver machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 800 may be a server computer, a clientcomputer, a personal computer (PC), a tablet computer, a laptopcomputer, a netbook, a set-top box (STB), a personal digital assistant(PDA), a cellular telephone, a smartphone, a web appliance, a networkrouter, a network switch, a network bridge, or any machine capable ofexecuting the instructions 824, sequentially or otherwise, that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude a collection of machines that individually or jointly executethe instructions 824 to perform any one or more of the methodologiesdiscussed herein.

The machine 800 includes a processor 802 (e.g., a central processingunit (CPU), a graphics processing unit (GPU), a digital signal processor(DSP), an application specific integrated circuit (ASIC), aradio-frequency integrated circuit (RFIC), or any suitable combinationthereof), a main memory 804, and a static memory 806, which areconfigured to communicate with each other via a bus 808. The machine 800may further include a graphics display 810 (e.g., a plasma display panel(PDP), a light emitting diode (LED) display, a liquid crystal display(LCD), a projector, or a cathode ray tube (CRT)). The machine 800 mayalso include an alphanumeric input device 812 (e.g., a keyboard), acursor control device 814 (e.g., a mouse, a touchpad, a trackball, ajoystick, a motion sensor, or other pointing instrument), a storage unit816, a signal generation device 818 (e.g., a speaker), and a networkinterface device 820.

The storage unit 816 includes a machine-readable medium 822 on which isstored the instructions 824 (e.g., software) embodying any one or moreof the methodologies or functions described herein. The instructions 824may also reside, completely or at least partially, within the mainmemory 804, within the processor 802 (e.g., within the processor's cachememory), or both, during execution thereof by the machine 800.Accordingly, the main memory 804 and the processor 802 may be consideredas machine-readable media. The instructions 824 may be transmitted orreceived over a network 826 via the network interface device 820. Thenetwork interface device 820 may be a wired transceiver or a wirelesstransceiver, including one or more transceivers that may be utilized ina cellular or mobile network, such as the mobile network 100.

As used herein, the term “memory” refers to a machine-readable mediumable to store data temporarily or permanently and may be taken toinclude, but not be limited to, random-access memory (RAM), read-onlymemory (ROM), buffer memory, flash memory, and cache memory. While themachine-readable medium 722 is shown in an example embodiment to be asingle medium, the term “machine-readable medium” should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storeinstructions. The term “machine-readable medium” shall also be taken toinclude any medium, or combination of multiple media, that is capable ofstoring instructions (e.g., software) for execution by a machine (e.g.,machine 700), such that the instructions, when executed by one or moreprocessors of the machine (e.g., processor 702), cause the machine toperform any one or more of the methodologies described herein.Accordingly, a “machine-readable medium” refers to a single storageapparatus or device, as well as “cloud-based” storage systems or storagenetworks that include multiple storage apparatus or devices. The term“machine-readable medium” shall accordingly be taken to include, but notbe limited to, one or more data repositories in the form of asolid-state memory, an optical medium, a magnetic medium, or anysuitable combination thereof.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium or ina transmission signal) or hardware modules. A “hardware module” is atangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware modules of a computer system (e.g., a processor or a groupof processors) may be configured by software (e.g., an application orapplication portion) as a hardware module that operates to performcertain operations as described herein.

In some embodiments, a hardware module may be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware module may include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware module may be a special-purpose processor, such as afieldprogrammable gate array (FPGA) or an ASIC. A hardware module may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwaremodule may include software encompassed within a general-purposeprocessor or other programmable processor. It will be appreciated thatthe decision to implement a hardware module mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software) may be driven by cost and timeconsiderations.

Accordingly, the phrase “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein,“hardware-implemented module” refers to a hardware module. Consideringembodiments in which hardware modules are temporarily configured (e.g.,programmed), each of the hardware modules need not be configured orinstantiated at any one instance in time. For example, where a hardwaremodule comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware modules) at different times. Software mayaccordingly configure a processor, for example, to constitute aparticular hardware module at one instance of time and to constitute adifferent hardware module at a different instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multiplehardware modules exist contemporaneously, communications may be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware modules. In embodiments inwhich multiple hardware modules are configured or instantiated atdifferent times, communications between such hardware modules may heachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware modules have access.For example, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e,g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented module” refers to ahardware module implemented using one or more processors.

Similarly, the methods described herein may be at least partiallyprocessor-implemented, a processor being an example of hardware. Forexample, at least some of the operations of a method may be performed byone or more processors or processor-implemented modules. Moreover, theone or more processors may also operate to support performance of therelevant operations in a “cloud computing” environment or as a “softwareas a service” (SaaS). For example, at least some of the operations maybe performed by a group of computers (as examples of machines includingprocessors), with these operations being accessible via a network (e.g.,the Internet) and via one or more appropriate interfaces (e.g., anapplication program interface (API)).

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

The above detailed description includes references to the accompanyingdrawings, which form a part of the detailed description. The drawingsshow, by way of illustration, specific embodiments in which theinvention can be practiced. These embodiments are also referred toherein as “examples.” Such examples can include elements in addition tothose shown or described However, the present inventors also contemplateexamples in which only those elements shown or described are provided.Moreover, the present inventors also contemplate examples using anycombination or permutation of those elements shown or described (or oneor more aspects thereof), either with respect to a particular example(or one or more aspects thereof), or with respect to other examples (orone or more aspects thereof) shown or described herein.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In this document, the terms “including” and “inwhich” are used as the plain-English equivalents of the respective terms“comprising” and “wherein.” Also, in the following claims, the terms“including” and “comprising” are open-ended, that is, a system, device,article, composition, formulation, or process that includes elements inaddition to those listed after such a term in a claim are still deemedto fall within the scope of that claim. Moreover, in the followingclaims, the terms “first,” “second,” and “third,” etc. are used merelyas labels, and are not intended to impose numerical requirements ontheir objects.

The above description is intended to be illustrative, and notrestrictive. For example, the above-described examples (or one or moreaspects thereof) may be used in combination with each other. Otherembodiments can be used such as by one of ordinary skill in the art uponreviewing the above description. The Abstract is provided to comply with37 C.F.R. §1.72(b), to allow the reader to quickly ascertain the natureof the technical disclosure. It is submitted with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. Also, in the above Detailed Description, various features may begrouped together to streamline the disclosure. This should not beinterpreted as intending that an unclaimed disclosed feature isessential to any claim. Rather, inventive subject matter may lie in lessthan all features of a particular disclosed embodiment. Thus, thefollowing claims are hereby incorporated into the Detailed Description,with each claim standing on its own as a separate embodiment, and it iscontemplated that such embodiments can be combined with each other invarious combinations or permutations. The scope of the invention shouldbe determined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

1. A user equipment (UE) configured for inter-RAT mobility, the UE comprising: a transceiver and processing circuit to: receive signaling to activate idle mode signal reduction (ISR) for subsequent use during inter-RAT cell re-selection while the UE is in idle mode; perform inter-RAT cell reselection in accordance with ISR when ISR is activated, the inter-RAT cell reselection to establish a circuit-switched (CS) radio signaling connection within a target cell when the target cell is a non-E-UTRAN cell; transmit signaling to suspend packet switched (PS) services while the UE has a signaling connection within a non-E-UTRAN cell; transmit signaling to initiate a tracking area update (TAU) procedure when ISR is activated to resume PS services when the UE returns to a E-UTRAN cell; and based on an unsuccessful resumption of PS services, deactivate ISR after returning to the E-UTRAN cell prior to initiating another TAU procedure to resume PS services.
 2. The UE of claim 1 wherein the UE is configured to deactivate ISR locally by setting a temporary identity used in next update (TIN) parameter of the UE to a value indicating a Packet-Temporary Mobile Scriber Identity (P-TMSI) before initiating the TAU procedure, wherein the P-TMSI refers to a RAT with the UE was established before the inter-RAT cell reselection.
 3. The UE of claim 2 further comprising a register, wherein the register is configured to store the P-TMSI.
 4. The UE of claim 2 wherein to perform the inter-RAT cell reselection in accordance with ISR, the UE is configured to refrain from initiating a routing area update (RAU) procedure when reselecting a GERAN cell of a routing area corresponding to a routing area identification that was stored by the UE during a last RAU procedure and a temporary identity used in next update (TIN) parameter of the UE is set to a value indicating a RAT-related Temporary Mobile Scriber Identity (TMSI).
 5. The UE of claim 4 wherein the signaling to activate ISR is received in a RAU or TAU accept message as part of a RAU or TAU procedure.
 6. The UE of claim 5 wherein the signaling to resume the PS services when the UE returns to a E-UTRAN cell is initiated by a TAU request message sent to a MME.
 7. The UE of claim 4 wherein when the non-E-UTRAN target cell is a GERAN cell, the UE is configured to, the UE is further configured to initiate CS call in the GERAN cell, wherein when the UE does not support dual-transfer mode (DTM) comprising simultaneous use of CS services and PS services, the UE is configured to transmit signaling to suspend PS services for the UE.
 8. The UE of claim 4 wherein the signaling to suspend PS services while the UE has a signaling connection within a non-E-UTRAN cell comprises a suspend request, wherein prior to transmission of the suspend request, the UE is configured to transmit an extended service request message in a E-UTRAN cell to initiate a circuit-switched fallback (CSFB) call, wherein transmission of the suspend request depends on whether the CSFB call is performed to a GERAN or a UTRAN target cell, and information conveyed by the suspend request depends on whether the ISR was activated before the CSFB call.
 9. The UE of claim 4 wherein the UE is configured to deactivate ISR after returning to the E-UTRAN cell when PS services were not resumed successfully prior to initiating a TAU procedure to resume PS services.
 10. The UE of claim 2 wherein the non-E-UTRAN target cell is either a UTRAN cell or a GERAN cell.
 11. The UE of claim 10 wherein when the non-E-UTRAN target cell is a GERAN cell, the UE is configured to transmit signaling to suspend the PS services while the UE is in dedicated mode and has a radio-resource (RR) signaling connection within the GERAN cell.
 12. The UE of claim 2 wherein the non-E-UTRAN target cell and the non-E-UTRAN cell with which the UE has a signaling connection are different non-E-UTRAN cells.
 13. The UE of claim 2 wherein the non-E-UTRAN target cell and the non-E-UTRAN cell with which the UE has a signaling connection are the same non-E-UTRAN cell.
 14. The UE of claim 2 wherein the UE is configured to receive signaling from a mobile management entity to suspend the PS services when the ISR is activated before a CSFB call.
 15. The UE of claim 2 further comprising two or more antennas configured to communicate with eNBs that provide cells with which the UE has a signaling connection with.
 16. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a user equipment (UE) to configure the UE to perform operations for inter-RAT cell reselection, the operations to configure the one or more processors to configure the UE to: receive signaling to activate idle mode signal reduction (ISR) for subsequent use during inter-RAT cell re-selection while the UE is in idle mode; perform inter-RAT cell reselection in accordance with ISR when ISR is activated, the inter-RAT cell reselection to establish a circuit-switched (CS) radio signaling connection within a target cell when the target cell is a non-E-UTRAN cell; transmit signaling to suspend packet switched (PS) services while the UE has a signaling connection within a non-E-UTRAN cell; transmit signaling to initiate a tracking area update (TAU) procedure when ISR is activated to resume PS services when the UE returns to a E-UTRAN cell; and based on an unsuccessful resumption of PS services, deactivate ISR after returning to the E-UTRAN cell prior to initiating another TAU procedure to resume PS services.
 17. The non-transitory computer-readable storage medium of claim 16 wherein the UE is configured to deactivate ISR locally by setting a temporary identity used in next update (TIN) parameter of the UE to a value indicating a Packet-Temporary Mobile Scriber Identity (P-TMSI) before initiating the TAU procedure, wherein the P-TMSI refers to a RAT with which the UE was established before the inter-RAT cell reselection.
 18. The non-transitory computer-readable storage medium of claim 17 wherein to perform the inter-RAT cell reselection in accordance with ISR, the UE is configured to refrain from initiating a routing area update (RAU) procedure when reselecting a GERAN cell of a routing area corresponding to a routing area identification that was stored by the UE during a last RAU procedure and a temporary identity used in next update (TIN) parameter of the UE is set to a value indicating a RAT-related Temporary Mobile Scriber Identity (TMSI).
 19. A user equipment (UE) configured for inter-RAT cell reselection, the UE comprising: a transceiver and processing circuitry configured to: transmit signaling to suspend packet switched (PS) services, after inter-RAT cell reselection, while the UE has a signaling connection within a non-E-UTRAN cell; initiate a tracking area update (TAU) procedure when idle mode signal reduction (ISR) is activated to resume PS services when the UE returns to a E-UTRAN cell; and based on PS services is not being resumed when the UE returns to the E-UTRAN cell, the UE is configured to deactivate ISR after returning to the E-UTRAN cell and set a temporary identity used in next update (TIN) parameter of the UE to a value indicating a Packet-Temporary Mobile Scriber Identity (P-TMSI) prior to initiating another TAU procedure to resume PS services.
 20. The UE of claim 19 further comprising memory for storing the P-TMSI, wherein the P-TMSI refers to a RAT with which the UE was established before the inter-RAT cell reselection.
 21. The UE of claim 20 wherein the UE, prior to inter-RAT cell reselection is configured to: receive signaling to activate ISR for subsequent use during inter-RAT cell re-selection while the UE is in idle mode; perform inter-RAT cell reselection in accordance with ISR when ISR is activated, the inter-RAT cell reselection to establish a circuit-switched (CS) radio signaling connection within a target cell when the target cell is a non-E-UTRAN cell. 